Rar window enhancement during random access procedure for new radio (nr)-unlicensed spectrum

ABSTRACT

Embodiments herein provide techniques for indication of a system frame number (SFN) in and/or associated with a random access response (RAR) for a random access procedure. A UE may transmit a physical random access channel (PRACH) preamble in a PRACH occasion (e.g., in a Msg 1  or MsgA) and monitor for a message (e.g., Msg 2  or MsgB) in a RAR window. The RAR window may be greater than one frame. The Msg 2  or MsgB (e.g., a downlink control information (DCI) and/or a medium access control (MAC) RAR) may indicate the SFN associated with the RACH occasion. The UE may determine whether the message is for the UE or another UE based on the SFN. Other embodiments may be described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 62/884,826, titled “ENABLING RAR WINDOW ENHANCEMENT DURING RANDOM ACCESS PROCEDURE FOR NR-UNLICENSED,” which was filed Aug. 9, 2019; U.S. Provisional Patent Application No. 62/887,447, titled “ENABLING RAR WINDOW ENHANCEMENT DURING RANDOM ACCESS PROCEDURE FOR NR-UNLICENSED,” which was filed Aug. 15, 2019; and U.S. Provisional Patent Application No. 62/910,041, titled “ENABLING RAR WINDOW ENHANCEMENT DURING RANDOM ACCESS PROCEDURE FOR NR-UNLICENSED,” which was filed Oct. 3, 2019, the disclosures of which are hereby incorporated by reference.

FIELD

Embodiments of the present invention relate generally to the technical field of wireless communications.

BACKGROUND

The channel access mechanism aspect is one of the fundamental building blocks for NR-unlicensed that is essential for any deployment options. The adoption of Listen-Before-Talk (LBT) in Long Term Evolution (LTE)-based License Assisted Access (LAA) system was crucial in achieving fair coexistence with the neighboring systems sharing the unlicensed spectrum, in addition to fulfilling the regulatory requirements. The LBT-based channel access mechanism fundamentally resembles the wireless local area network (WLAN) Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) principles. Any node that intends to transmit in unlicensed spectrum may first perform a channel sensing operation before initiating any transmission. An additional random back-off mechanism is adopted to avoid collisions when more than one node senses the channel as idle and transmits simultaneously.

In New Radio (NR), a user equipment (UE) in idle/inactive state accesses the network to request connection set-up through a series of functions/procedures commonly known as a random access process. Similar functionality may be used by a UE in connected mode as well, for example, for re-establishing uplink synchronization. NR uses a four-step random access procedure for contention based random access (CBRA) and a two-step random access procedure for contention free random access (CFRA).

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

FIG. 1 illustrates a medium access control (MAC) random access response (RAR) message that includes an indication of a subframe number (SFN), in accordance with various embodiments.

FIG. 2 illustrates another MAC RAR message that includes an indication of a SFN, in accordance with various embodiments.

FIG. 3 illustrates an operation flow/algorithmic structure in accordance with some embodiments.

FIG. 4 illustrates another operation flow/algorithmic structure in accordance with some embodiments.

FIG. 5 illustrates an example architecture of a system of a network, in accordance with various embodiments.

FIG. 6 illustrates an example of infrastructure equipment in accordance with various embodiments.

FIG. 7 illustrates an example of a platform in accordance with various embodiments.

FIG. 8 illustrates example components of baseband circuitry and radio front end modules, in accordance with various embodiments.

FIG. 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (for example, a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense.

Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.

For the purposes of the present disclosure, the phrases “A or B” and “A and/or B” mean (A), (B), or (A and B). For the purposes of the present disclosure, the phrases “A, B, or C” and “A, B, and/or C” mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

The description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

As used herein, the term “circuitry” may refer to, be part of, or include any combination of integrated circuits (for example, a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), discrete circuits, combinational logic circuits, system on a chip (SOC), system in a package (SiP), that provides the described functionality. In some embodiments, the circuitry may execute one or more software or firmware modules to provide the described functions. In some embodiments, circuitry may include logic, at least partially operable in hardware.

Embodiments herein provide techniques for indication of a system frame number (SFN) in and/or associated with a random access response (RAR) for a random access procedure. A UE may transmit a physical random access channel (PRACH) preamble in a RACH occasion. For example, the PRACH preamble may be transmitted in a message 1 (Msg1) of a 4-step random access procedure and/or a message A (MsgA) of a 2-step random access procedure. The UE may monitor for a message in a RAR window based on the PRACH preamble. The message may be, for example, a message 2 (Msg2) of the 4-step random access procedure or a message B (MsgB) of the 2-step random access procedure. The message may include a downlink control information (DCI) and/or a medium access control RAR. For example, the DCI may schedule a PDSCH in which the MAC RAR is transmitted (e.g., the DCI may indicate a resource allocation for the MAC RAR).

In various embodiments, the RAR window may be greater than one frame. The message received in the RAR window (e.g., the DCI and/or the MAC RAR) may indicate the SFN associated with the RACH occasion. The UE may determine whether the message is for the UE or another UE based on the SFN.

In New Radio (NR), a UE (e.g., the UE 501 a-b of FIG. 5) in idle/inactive state access the network to request typically for connection set-up through a series of functions/procedures with an access node of the radio access network (RAN) (e.g., RAN node 511 a-b), commonly known as random access process. Similar functionality may be used by a UE in connected mode as well, for example, for re-establishing uplink synchronization. NR uses a four-step random access procedure for contention based random access (CBRA) and a two-step random access procedure for contention free random access (CFRA). For CBRA, the random access procedure includes the following operations:

-   -   Operation 1 (Message 1 transmission): UE transmits a preamble,         also known as physical random access channel (PRACH).     -   Operation 2 (Message 2 transmission): network (e.g., gNB)         transmits a DCI and associated RAR message indicating reception         of the preamble and providing timing alignment command (e.g.,         based on the timing of the received preamble) for the UE to         adjust its transmission timing.     -   Operation 3 (Message 3 transmission): UE transmits uplink radio         resource control (RRC) connection request based on the uplink         (UL) grant provided by RAR.     -   Operation 4 (Message 4 transmission): network (e.g., gNB)         transmits contention resolution in downlink (DL). The contention         resolution may resolve any potential collision due to         simultaneous transmission of the same preamble from multiple         devices within the cell. If successful, message 4 also transfers         the UE to connected state.

To fulfill regulatory requirements and provide a global solution of unified framework, NR-based unlicensed access will also use Listen-Before-Talk (LBT)-based channel access mechanisms. Due to LBT, the transmission of message 1/2/3/4 during contention based random access procedure (CBRA) can be impacted, while operating in unlicensed spectrum. For example, LBT may need to be performed at the User Equipment (UE) side before PRACH preamble can be transmitted or at gNB side before random access response (RAR) in response to preamble reception can be transmitted. The window for receiving RAR by UE in NR-licensed system, which does not need to cope with such channel access related contention, therefore, may not be sufficient for random access procedure in unlicensed spectrum.

Various embodiments herein provide enhancements of Message 2 (RAR) window to cope with LBT related congestion for Message 2 (Msg2) transmission and enhancing opportunity for receiving RAR at the UE side in unlicensed spectrum. For example, embodiments provide enhancement of RAR window to take into account LBT congestion related delay in RAR transmission; and details of signaling aspects related to RAR window enhancement for unlicensed operation.

The message sent by the gNB in the RAR window (e.g., Msg2) may include a downlink control information (DCI) and/or a medium access control (MAC) RAR message (e.g., a MAC sub-packet data unit (PDU)). The UE may monitor for the RAR message in the RAR window after transmitting the PRACH preamble. For example, the UE may attempt to detect a DCI format 1_0 with Cyclic Redundancy Checksum (CRC) scrambled by a corresponding Radio Network Temporary Identifier (RNTI), such as a Random Access-RNTI (RA-RNTI), during the RAR window. The RAR window may be controlled by higher layers. For example, in some embodiments, the RAR window starts at the first symbol of the earliest COntrol REsource SET (CORESET) on which the UE is configured to receive Physical Downlink Control Channel (PDCCH) for Type 1-PDCCH Common Search Space (CSS) set, that is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. The symbol duration may correspond to the subcarrier spacing (SCS) for Type 1-PDCCH CSS set.

The length of the RAR window in number of slots, based on the SCS for Type 1-PDCCH CSS set, is provided by ra-ResponseWindow in 3GPP TS 38.331 v15.5.1 as follows:

RACH-ConfigGeneric information element -- ASN1START -- TAG-RACH-CONFIGGENERIC-START RACH-ConfigGeneric ::= SEQUENCE {  prach-ConfigurationIndex INTEGER (0..255),  msg1-FDM ENUMERATED {one, two, four, eight},  msg1-FrequencyStart INTEGER (0..maxNrofPhysicalRe-  sourceBlocks-1),  zeroCorrelationZoneConfig INTEGER(0..15),  preambleReceivedTargetPower INTEGER (−202..−60),  preambleTransMax ENUMERATED {n3, n4, n5, n6, n7,  n8, n10, n20, n50, n100, n200},  powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},  ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8,  sl10, sl20, sl40, sl80},  ... } -- TAG-RACH-CONFIGGENERIC-STOP -- ASN1STOP

RACH-ConfigGeneric field descriptions msg1-FDM The number of PRACH transmission occasions FDMed in one time instance. (see 3GPP TS 38.211, clause 6.3.3.2). msg1-FrequencyStart Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see 3GPP TS 38.211, clause 6.3.3.2). powerRampingStep Power ramping steps for PRACH (see 3GPP TS 38.321, 5.1.3). prach-ConfigurationIndex PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecovery-Config, the prach- ConfigurationIndex can only correspond to the short preamble format (see 3GPP TS 38.211, clause 6.3.3.2). preambleReceivedTargetPower The target power level at the network receiver side (see 3GPP TS 38.213, clause 7.4, 3GPP TS 38.321, clauses 5.1.2, 5.1.3). Only multiples of 2 dBm may be chosen (e.g. −202, −200, −198, . . . ). preambleTransMax Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). ra-Response Window Msg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms (see 3GPP TS 38.321, clause 5.1.4). UE ignores the field if included in SCellConFigure zeroCorrelationZoneConfig N-CS configuration, see Table 6.3.3.1-5 in 3GPP TS 38.211.

In NR-unlicensed operations, transmission of RAR may be hindered by LBT congestion at gNB side, causing additional delay in RAR reception at the UE side. Therefore, if the RAR window length as used in NR (10 ms) is kept the same, unnecessary PRACH transmission may be triggered due to not receiving RAR within the RAR window because of the delay in RAR transmission from gNB due to delay in channel access (even though gNB successfully received preamble). To take into account this possible delay in RAR transmission in unlicensed operation, the RAR window size may be extended for NR-unlicensed operation. For example, the size of the RAR window in NR-unlicensed operation may be 20 ms (e.g., 2 radio frames) to 40 ms (e.g., 4 radio frames) or more.

The RA-RNTI associated with the PRACH occasion in which the Random Access Preamble is transmitted, is computed as:

RA-RNTI = 1 − s_id + (max   # s_id) × t_id + (max   # s_id) × (max   #t_id) × f_id + (max   # s_id) × (max   # t_id) × (max   # f_id) × ul_carrier_id = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id

wherein s_id is the index of the first OFDM symbol of the PRACH occasion (0≤s_id<14), t_id is the index of the first slot of the PRACH occasion in a system frame (0≤t_id<80), where the subcarrier spacing to determine t_id is based on the value of μ specified in subclause 5.3.2 in 3GPP TS 38.211 v15.5.0, f_id is the index of the PRACH occasion in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Random Access Preamble transmission (e.g., 0 for normal uplink (NUL) carrier, and 1 for supplementary uplink (SUL) carrier).

RA-RNTI calculation may not take into account System Frame Number (SFN) in NR, since max configurable RAR window size in NR is 10 ms (1 frame) and the minimum periodicity with which same RACH transmission occasion (RO) (e.g. same RA-RNTI) can occur is 10 ms or 1 frame as well (e.g., n_(SFN) mod x=y; x=1, y=0), which implies that within the RAR window, RA-RNTIs are unique.

However, with enhancement of RAR window size beyond 10 ms, there may be a possibility with the current NR RA-RNTI calculation framework that multiple ROs corresponding to the same RA-RNTI may occur within the extended RAR window. Hence, if more than one UE happens to use these ROs for preamble transmission, then due to overlap in their RAR window it may happen that RAR with the same RA-RNTI may be received within the overlapping RAR zone by these UEs and there would be no way to distinguish between these RARs unless these RA-RNTIs are made unique or SFN corresponding to each RO (e.g., having same RA-RNTI) is conveyed. The following embodiments provide mechanisms to convey the SFN. For example, an indication of the SFN may be included in the message transmitted in the RAR window (e.g., Msg2 or MsgB), such as in the DCI and/or MAC RAR.

Enhancement of RAR to Incorporate SFN

In embodiments, Msg2 may be enhanced to take into account enhanced RAR window size during random access procedure in NR-unlicensed. In embodiments, SFN may be provided as a part of the DCI (e.g., DCI format 1_0). In one option, if the CRC of the DCI format 1_0 is scrambled by RA-RNTI, the DCI format 1_0 is for contention based random access procedure, for which there are “16” reserved bits. Out of these 16 bits, n-bits (n≤16) can be used to indicate SFN, where n=┌log₂{R/10}┐, where R is the value of ra-Response Window (expressed in ms) and R≤(2^(n)·10) ms where n is the number of available bits to indicate SFN. The table below shows the bit fields in DCI format 1_0 scrambled with RA-RNTI and the necessary modifications show in bold and underline to indicate inclusion of SFN in DCI format 1_0 content:

TABLE 2 Modified DCI 1 0 field contents (scrambled by RA-RNTI) DCI 1_0 bit fields Number of bits Frequency domain ┌log₂ (N_(RB) ^(DL)

^(BWP) (N_(RB) ^(DL)

^(BWP) + 1)/2)┐ resource assignment Time domain resource 4 assignment VRB-to-PRB mapping 1 Modulation and coding 5 scheme TB scaling 2 SFN n (1 ≤ n ≤ 16) Reserved bits

 16 − n

indicates data missing or illegible when filed

As one example, for R=20 ms, n=1, hence 1-bit will be assigned for SFN bit field, whereas 15 bits may remain as reserved bits. In another example, R=40 ms, n=2, so 2 bits will be designated for SFN bit field and 14 bits may remain as reserved bits.

In other embodiments, SFN information may be included as a part of the MAC RAR message. In one option, if the RAR window size is increased such that R_(max)≤20 ms, only 1-bit is required to indicate SFN. In some embodiments, the existing MAC RAR octet format can be used to indicate the SFN (e.g., 1-bit SFN) as shown in FIG. 1. For example, the SFN indication may utilize a previously reserved bit. In some embodiments, the SFN indication may be included in Octet 1 of the MAC RAR.

In another option, e.g., if RAR window size is increased beyond the duration of 2 frames, such that more than 1-bit indication of SFN is required, bits from the RAR UL grant field (total 27 bits in NR) may be omitted and repurposed for SFN indication. As one example, 1˜6 bits may be omitted from RAR UL grant fields (as one example, 1-bit from “frequency hopping flag field, 1-bit from “CSI request” field and 4-bits from “PUSCH frequency resource allocation field etc.) and assigned for SFN indication. For example, a modified MAC RAR with 3-bits assigned to SFN indication is illustrated in FIG. 2.

In another option, SFN information (e.g., with n bits) is indicated through a part of the uplink grant field. In this case, the total number of bits for uplink grant field is reduced to 27-n bits. Accordingly, some bits of the uplink grant field may be repurposed for SFN information.

In another option, SFN information (n bits) is indicated through a part of the timing advance command. In this case, the total number of bits for timing advanced command is reduced to 12-n bits. This may be based on the assumption that NR-unlicensed is typically not used for very large cell scenario and the largest values of the previous timing advance (TA) field (e.g., with 12 bits) are not required.

The techniques described herein may also be used for the 2-step random access procedure. In the 2-step random access procedure, the UE may transmit MsgA including a PRACH preamble and PUSCH. The gNB may transmit MsgB in the RAR window. The MsgB may include a DCI scrambled with a MsgB-RNTI.

In embodiments, when the 2-step random access procedure is applied for NR system operating in unlicensed spectrum, successRAR and/or fallbackRAR may be included in MsgB. in some embodiments, SuccessRAR may be included when gNB successfully detects MsgA PRACH preamble and decodes MsgA PUSCH for a UE while fallbackRAR may be included when gNB successfully detects MsgA PRACH preamble but fails to decode MsgA PUSCH, and subsequently informs UE to switch from 2-step random access procedure to 4-step random access procedure.

For fallbackRAR, similar to Msg2 in 4-step RACH procedure, SFN information may be explicitly included in DCI or MAC subPDU. More specifically, the above embodiments for carrying SFN information in the DCI or MAC subPDU in Msg2 may be employed to carry SFN information in fallbackRAR.

For successRAR, SFN information may be explicitly indicated in the MAC subPDU. It may be included without changing the size of other fields in successRAR. For instance, it may be included prior to or after the TA command (e.g., 12 bits) and the UE contention resolution ID (e.g., 48 bits).

In embodiments, the RA-RNTI computation may be enhanced to incorporate SFN information in order to generate unique RA-RNTI within extended RAR window. As one example, for RAR window size extended up to 20 ms, the RA-RNTI calculation in existing Rel-15 NR licensed system can be enhanced to incorporate the 1-bit least significant bit (LSB) of SFN as follows:

RA-RNTI=1+(s_id+SFN mod2)+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where, SFN mod2 essentially signifies 1-bit LSB of SFN for 20 ms RAR window size.

FIG. 3 illustrates an operation flow/algorithmic structure 300 in accordance with some embodiments. The operation flow/algorithmic structure 300 may be performed, in part or in whole, by a UE (e.g., UE 501 a-b, discussed infra), or components thereof. For example, in some embodiments, the operation flow/algorithmic structure 300 may be performed by the baseband circuitry implemented in the UE.

At 304, the operation flow/algorithmic structure 300 may include encoding, for transmission to a gNB of a wireless cellular network on unlicensed spectrum, a PRACH preamble in a PRACH occasion.

At 308, the operation flow/algorithmic structure 300 may include determining a RAR window based on the PRACH occasion.

At 312, the operation flow/algorithmic structure 300 may include receiving a message in the RAR window, wherein the message includes a SFN indicator to indicate that the response message corresponds to the PRACH occasion. For example, the SFN indicator may be included in a DCI (e.g., DCI format 0_1) of the message and/or in a MAC RAR (e.g., MAC subPDU) of the message. The message may be, for example, a Msg2 of the 4-step random access procedure or a MsgB of the 2-step random access procedure.

In some embodiments, the SFN indicator may be 1 bit to indicate the SFN from among 2 frames (e.g., for a RAR window length of 2 frames (20 ms). In other embodiments, the SFN indicator may be 2 bits to indicate the SFN from among 4 frames (e.g., for a RAR window length of 4 frames (40 ms). It will be apparent that other numbers of bits and/or RAR window lengths may be used. In some embodiments, the SFN indicator of size n bit(s) may include the n least significant bits of the SFN in which the PRACH occasion occurs and/or that otherwise corresponds to the PRACH occasion (e.g., the SFN of the first frame of the associated RAR window).

At 316, the operation flow/algorithmic structure 300 may include processing the message based on the SFN indicator. For example, the UE may determine that the message is for the UE (e.g., rather than another UE) based on the SFN indicator.

FIG. 4 illustrates another operation flow/algorithmic structure 400 in accordance with various embodiments. The operation flow/algorithmic structure 400 may be performed, in part or in whole, by a gNB (e.g., RAN nodes 511 a-b, discussed infra), or components thereof. For example, in some embodiments the operation flow/algorithmic structure 400 may be performed by the baseband circuitry implemented in the gNB.

At 404, the operation flow/algorithmic structure 400 may include receiving, from a UE on unlicensed spectrum, a PRACH preamble in a PRACH occasion.

At 408, the operation flow/algorithmic structure 400 may further include determining a RAR window based on the PRACH occasion.

At 412, the operation flow/algorithmic structure 400 may further include encoding a response message for transmission to the UE in the RAR window, wherein the response message includes a SFN indicator to indicate that the response message corresponds to the PRACH occasion. For example, the SFN indicator may be included in a DCI (e.g., DCI format 0_1) of the response message and/or in a MAC RAR (e.g., MAC subPDU) of the response message. The response message may be, for example, a Msg2 of the 4-step random access procedure or a MsgB of the 2-step random access procedure.

In some embodiments, the SFN indicator may be 1 bit to indicate the SFN from among 2 frames (e.g., for a RAR window length of 2 frames (20 ms). In other embodiments, the SFN indicator may be 2 bits to indicate the SFN from among 4 frames (e.g., for a RAR window length of 4 frames (40 ms). It will be apparent that other numbers of bits and/or RAR window lengths may be used. In some embodiments, the SFN indicator of size n bit(s) may include the n least significant bits of the SFN in which the PRACH occasion occurs and/or that otherwise corresponds to the PRACH occasion (e.g., the SFN of the first frame of the associated RAR window).

Systems and Implementations

FIG. 5 illustrates an example architecture of a system 500 of a network, in accordance with various embodiments. The following description is provided for an example system 500 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As shown by FIG. 5, the system 500 includes UE 501 a and UE 501 b (collectively referred to as “UEs 501” or “UE 501”). In this example, UEs 501 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and/or the like.

In some embodiments, any of the UEs 501 may be IoT UEs, which may comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network. In some of these embodiments, the UEs 501 may be NB-IoT UEs 501. NB-IoT provides access to network services using physical layer optimized for very low power consumption (e.g., full carrier BW is 180 kHz, subcarrier spacing can be 3.75 kHz or 15 kHz). A number of E-UTRA functions are not used for NB-IoT and need not be supported by RAN nodes 511 and UEs 501 only using NB-IoT. Examples of such E-UTRA functions may include inter-RAT mobility, handover, measurement reports, public warning functions, GBR, CSG, support of HeNBs, relaying, carrier aggregation, dual connectivity, NAICS, MBMS, real-time services, interference avoidance for in-device coexistence, RAN assisted WLAN interworking, sidelink communication/discovery, MDT, emergency call, CS fallback, self-configuration/self-optimization, among others. For NB-IoT operation, a UE 501 operates in the DL using 12 sub-carriers with a sub-carrier BW of 15 kHz, and in the UL using a single sub-carrier with a sub-carrier BW of either 3.75 kHz or 15 kHz or alternatively 3, 6 or 12 sub-carriers with a sub-carrier BW of 15 kHz.

In various embodiments, the UEs 501 may be MF UEs 501. MF UEs 501 are LTE-based UEs 501 that operate (exclusively) in unlicensed spectrum. This unlicensed spectrum is defined in MF specifications provided by the MulteFire Forum, and may include, for example, 1.9 GHz (Japan), 3.5 GHz, and 5 GHz. MulteFire is tightly aligned with 3GPP standards and builds on elements of the 3GPP specifications for LAA/eLAA, augmenting standard LTE to operate in global unlicensed spectrum. In some embodiments, LBT may be implemented to coexist with other unlicensed spectrum networks, such as WiFi, other LAA networks, or the like. In various embodiments, some or all UEs 501 may be NB-IoT UEs 501 that operate according to MF. In such embodiments, these UEs 501 may be referred to as “MF NB-IoT UEs 501,” however, the term “NB-IoT UE 501” may refer to an “MF UE 501” or an “MF and NB-IoT UE 501” unless stated otherwise. Thus, the terms “NB-IoT UE 501,” “MF UE 501,” and “MF NB-IoT UE 501” may be used interchangeably throughout the present disclosure.

The UEs 501 may be configured to connect, for example, communicatively couple, with an or RAN 510. In embodiments, the RAN 510 may be an NG RAN or a 5G RAN, an E-UTRAN, an MF RAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to a RAN 510 that operates in an NR or 5G system 500, the term “E-UTRAN” or the like may refer to a RAN 510 that operates in an LTE or 4G system 500, and the term “MF RAN” or the like refers to a RAN 510 that operates in an MF system 100. The UEs 501 utilize connections (or channels) 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below). The connections 103 and 104 may include several different physical DL channels and several different physical UL channels. As examples, the physical DL channels include the PDSCH, PMCH, PDCCH, EPDCCH, MPDCCH, R-PDCCH, SPDCCH, PBCH, PCFICH, PHICH, NPBCH, NPDCCH, NPDSCH, and/or any other physical DL channels mentioned herein. As examples, the physical UL channels include the PRACH, PUSCH, PUCCH, SPUCCH, NPRACH, NPUSCH, and/or any other physical UL channels mentioned herein.

In this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs 501 may directly exchange communication data via a ProSe interface 505. The ProSe interface 505 may alternatively be referred to as a SL interface 505 and may comprise one or more physical and/or logical channels, including but not limited to the PSCCH, PSSCH, PSDCH, and PSBCH.

The UE 501 b is shown to be configured to access an AP 506 (also referred to as “WLAN node 506,” “MILAN 506,” “MILAN Termination 506,” “WT 506” or the like) via connection 507. The connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 501 b, RAN 510, and AP 506 may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE 50 lb in RRC_CONNECTED being configured by a RAN node 511 a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 501 b using WLAN radio resources (e.g., connection 507) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 507. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN 510 can include one or more AN nodes or RAN nodes 511 a and 511 b (collectively referred to as “RAN nodes 511” or “RAN node 511”) that enable the connections 503 and 504. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, MF-APs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node 511 that operates in an NR or 5G system 500 (e.g., a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node 511 that operates in an LTE or 4G system 500 (e.g., an eNB). According to various embodiments, the RAN nodes 511 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher BW compared to macrocells.

In some embodiments, all or parts of the RAN nodes 511 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes 511; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes 511; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes 511. This virtualized framework allows the freed-up processor cores of the RAN nodes 511 to perform other virtualized applications. In some implementations, an individual RAN node 511 may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by FIG. 5). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs (see e.g., FIG. 6), and the gNB-CU may be operated by a server that is located in the RAN 510 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes 511 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs 501, and are connected to a 5GC via an NG interface (discussed infra). In MF implementations, the MF-APs 511 are entities that provide MulteFire radio services, and may be similar to eNBs 511 in an 3GPP architecture. Each MF-AP 511 includes or provides one or more MF cells.

In V2X scenarios one or more of the RAN nodes 511 may be or act as RSUs. The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs 501 (vUEs 501). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. The computing device(s) and some or all of the radiofrequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.

Any of the RAN nodes 511 can terminate the air interface protocol and can be the first point of contact for the UEs 501. In some embodiments, any of the RAN nodes 511 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In embodiments, the UEs 501 can be configured to communicate using OFDM communication signals with each other or with any of the RAN nodes 511 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

Downlink and uplink transmissions may be organized into frames with 10 ms durations, where each frame includes ten 1 ms subframes. A slot duration is 14 symbols with Normal CP and 12 symbols with Extended CP, and scales in time as a function of the used sub-carrier spacing so that there is always an integer number of slots in a subframe. In LTE implementations, a DL resource grid can be used for DL transmissions from any of the RAN nodes 511 to the UEs 501, while UL transmissions from the UEs 501 to RAN nodes 511 can utilize a suitable UL resource grid in a similar manner. These resource grids may refer to time-frequency grids, and indicate physical resource in the DL or UL in each slot. Each column and each row of the DL resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively, and each column and each row of the UL resource grid corresponds to one SC-FDMA symbol and one SC-FDMA subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The resource grids comprises a number of RBs, which describe the mapping of certain physical channels to REs. In the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. Each RB comprises a collection of REs. An RE is the smallest time-frequency unit in a resource grid. Each RE is uniquely identified by the index pair (k,l) in a slot where k=0, . . . , N_(RB) ^(DL)N_(sc) ^(RB)−1 and l=0, . . . , N_(symb) ^(DL)−1 are the indices in the frequency and time domains, respectively. RE (k,l) on antenna port p corresponds to the complex value a_(k,l) ^((p)). An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. There is one resource grid per antenna port. The set of antenna ports supported depends on the reference signal configuration in the cell, and these aspects are discussed in more detail in 3GPP TS 36.211.

In NR/5G implementations, DL and UL transmissions are organized into frames with 10 ms durations each of which includes ten 1 ms subframes. The number of consecutive OFDM symbols per subframe is N_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). Each frame is divided into two equally-sized half-frames of five subframes each with a half-frame 0 comprising subframes 0-4 and a half-frame 1 comprising subframes 5-9. There is one set of frames in the UL and one set of frames in the DL on a carrier. Uplink frame number i for transmission from the UE 501 starts T_(TA)=(N_(TA)+N_(TA,offset))T_(c) before the start of the corresponding downlink frame at the UE where N_(TA,offset) is given by 3GPP TS 38.213. For subcarrier spacing configuration μ, slots are numbered n_(s) ^(μ) ϵ{0, . . . , N_(slot) ^(subframe,μ)−1} in increasing order within a subframe and n_(s,f) ^(μ) ϵ{0, . . . , N_(slot) ^(frame,μ)−1} in increasing order within a frame. There are N_(symb) ^(slot) consecutive OFDM symbols in a slot where N_(symb) ^(slot) depends on the cyclic prefix as given by tables 4.3.2-1 and 4.3.2-2 of 3GPP TS 38.211. The start of slot n_(s) ^(μ) in a subframe is aligned in time with the start of OFDM symbol n_(s) ^(μ)N_(symb) ^(slot) in the same subframe. OFDM symbols in a slot can be classified as ‘downlink’, ‘flexible’, or ‘uplink’, where downlink transmissions only occur in ‘downlink’ or ‘flexible’ symbols and the UEs 501 only transmit in ‘uplink’ or ‘flexible’ symbols.

For each numerology and carrier, a resource grid of N_(grid,x) ^(size,μ)N_(sc) ^(RB) subcarriers and N_(symb) ^(subframe,μ) OFDM symbols is defined, starting at common RB N_(grid) ^(start,μ) indicated by higher-layer signaling. There is one set of resource grids per transmission direction (i.e., uplink or downlink) with the subscript x set to DL for downlink and x set to UL for uplink. There is one resource grid for a given antenna port p, subcarrier spacing configuration μ, and transmission direction (i.e., downlink or uplink).

An RB is defined as N_(sc) ^(RB)=12 consecutive subcarriers in the frequency domain. Common RBs are numbered from 0 and upwards in the frequency domain for subcarrier spacing configuration μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ coincides with ‘point A’. The relation between the common resource block number n_(CRB) ^(μ) in the frequency domain and resource elements (k, l) for subcarrier spacing configuration μ is given by

$n_{CRB}^{\mu} = \left\lfloor \frac{k}{N_{sc}^{RB}} \right\rfloor$

where k is defined relative to point A such that k=0 corresponds to the subcarrier centered around point A. Point A serves as a common reference point for resource block grids and is obtained from offsetToPointA for a PCell downlink where offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which has the subcarrier spacing provided by the higher-layer parameter subCarrierSpacingCommon and overlaps with the SS/PBCH block used by the UE for initial cell selection, expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2; and absoluteFrequencyPointA for all other cases where absoluteFrequencyPointA represents the frequency-location of point A expressed as in ARFCN.

A PRB for subcarrier configuration μ are defined within a BWP and numbered from 0 to N_(BWP,i) ^(size,μ)−1 where i is the number of the BWP. The relation between the physical resource block n_(PRB) ^(μ) in BWPi and the common RB n_(CRB) ^(μ) is given by n_(CRB) ^(μ)=n_(PRB) ^(μ)+N_(BWP,i) ^(start,μ) where N_(BWP,i) ^(start,μ) is the common RB where BWP starts relative to common RB 0. VRBs are defined within a BWP and numbered from 0 to N_(BWP,i) ^(size)−1 where i is the number of the BWP.

Each element in the resource grid for antenna port p and subcarrier spacing configuration μ is called an RE and is uniquely identified by (k, l)_(p,μ) where k is the index in the frequency domain and l refers to the symbol position in the time domain relative to some reference point. Resource element (k, l)_(p,μ) corresponds to a physical resource and the complex value a_(k,l) ^((p,μ)). An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. Two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

A BWP is a subset of contiguous common resource blocks defined in subclause 4.4.4.3 of 3GPP TS 38.211 for a given numerology μ_(i) in BWP^(i) on a given carrier. The starting position N_(BWP,i) ^(start,μ) and the number of resource blocks N_(BWP,i) ^(size,μ) in a BWP shall fulfil N_(grid,x) ^(start,μ)≤N_(BWP,i) ^(start,μ)<N_(grid,x) ^(start,μ)+N_(grid,x) ^(size,μ) and N_(grid,x) ^(start,μ)<N_(BWP,i) ^(start,μ)+N_(BWP,i) ^(size,μ)≤N_(grid,x) ^(start,μ)+N_(grid,x) ^(size,μ), respectively. Configuration of a BWP is described in clause 12 of 3GPP TS 38.213. The UEs 501 can be configured with up to four BWPs in the DL with a single DL BWP being active at a given time. The UEs 501 are not expected to receive PDSCH, PDCCH, or CSI-RS (except for RRM) outside an active BWP. The UEs 501 can be configured with up to four BWPs in the UL with a single UL BWP being active at a given time. If a UE 501 is configured with a supplementary UL, the UE 501 can be configured with up to four additional BWPs in the supplementary UL with a single supplementary UL BWP being active at a given time. The UEs 501 do not transmit PUSCH or PUCCH outside an active BWP, and for an active cell, the UEs do not transmit SRS outside an active BWP.

An NB is defined as six non-overlapping consecutive PRBs in the frequency domain. The total number of DL NBs in the DL transmission BW configured in the cell is given by

$N_{NB}^{DL} = {\left\lfloor \frac{N_{RB}^{DL}}{6} \right\rfloor.}$

The NBs are numbered n_(NB)=0, . . . , N_(RB) ^(DL)−1 in order of increasing PRB number where narrowband n_(NB) is comprises PRB indices:

$\left\{ {\begin{matrix} {{{6n_{NB}} + i_{0} + i}\mspace{34mu}} & {{{{if}\mspace{14mu} N_{RB}^{UL}\mspace{14mu} {mod}\mspace{14mu} 2} = 0}\mspace{194mu}} \\ {{{6n_{NB}} + i_{0} + i}\mspace{40mu}} & {{{if}\mspace{14mu} N_{RB}^{UL}\mspace{14mu} {mod}\mspace{14mu} 2} = {{1\mspace{14mu} {and}\mspace{14mu} n_{NB}} < {N_{NB}^{UL}\text{/}2}}} \\ {{6n_{NB}} + i_{0} + i + 1} & {{{if}\mspace{14mu} N_{RB}^{UL}\mspace{14mu} {mod}\mspace{14mu} 2} = {{1\mspace{14mu} {and}\mspace{14mu} n_{NB}} \geq {N_{NB}^{UL}\text{/}2}}} \end{matrix},{{{where}i} = 0},1,\ldots \;,{{5i_{0}} = {\left\lfloor \frac{N_{RB}^{UL}}{2} \right\rfloor - {\frac{6N_{NB}^{UL}}{2}.}}}} \right.$

If N_(NB) ^(UL)≥4, a wideband is defined as four non-overlapping narrowbands in the frequency domain. The total number of uplink widebands in the uplink transmission bandwidth configured in the cell is given by

$N_{WB}^{UL} = \left\lfloor \frac{N_{NB}^{UL}}{4} \right\rfloor$

and the widebands are numbered n_(WB)=0, . . . , N_(WB) ^(UL)−1 in order of increasing narrowband number where wideband n_(WB) is composed of narrowband indices 4n_(WB)+i where i=0,1, . . . , 3. If N_(NB) ^(UL)<4, then N_(WB) ^(UL)=1 and the single wideband is composed of the N_(NB) ^(UL) non-overlapping narrowband(s).

There are several different physical channels and physical signals that are conveyed using RBs and/or individual REs. A physical channel corresponds to a set of REs carrying information originating from higher layers. Physical UL channels may include PUSCH, PUCCH, PRACH, and/or any other physical UL channel(s) discussed herein, and physical DL channels may include PDSCH, PBCH, PDCCH, and/or any other physical DL channel(s) discussed herein. A physical signal is used by the physical layer (e.g., PHY XV10 of Figure XV) but does not carry information originating from higher layers. Physical UL signals may include DMRS, PTRS, SRS, and/or any other physical UL signal(s) discussed herein, and physical DL signals may include DMRS, PTRS, CSI-RS, PSS, SSS, and/or any other physical DL signal(s) discussed herein.

The PDSCH carries user data and higher-layer signaling to the UEs 501. Typically, DL scheduling (assigning control and shared channel resource blocks to the UE 501 within a cell) may be performed at any of the RAN nodes 511 based on channel quality information fed back from any of the UEs 501. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501. The PDCCH uses CCEs to convey control information (e.g., DCI), and a set of CCEs may be referred to a “control region.” Control channels are formed by aggregation of one or more CCEs, where different code rates for the control channels are realized by aggregating different numbers of CCEs. The CCEs are numbered from 0 to N_(CCE,k)−1, where N_(CCE,k)−1 is the number of CCEs in the control region of subframe k. Before being mapped to REs, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical REs known as REGs. Four QPSK symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8 in LTE and L=1, 2, 4, 8, or 16 in NR). The UE 501 monitors a set of PDCCH candidates on one or more activated serving cells as configured by higher layer signaling for control information (e.g., DCI), where monitoring implies attempting to decode each of the PDCCHs (or PDCCH candidates) in the set according to all the monitored DCI formats (e.g., DCI formats 0 through 6-2 as discussed in section 5.3.3 of 3GPP TS 38.212, DCI formats 0_0 through 2_3 as discussed in section 7.3 of 3GPP TS 38.212, or the like). The UEs 501 monitor (or attempt to decode) respective sets of PDCCH candidates in one or more configured monitoring occasions according to the corresponding search space configurations. A DCI transports DL, UL, or SL scheduling information, requests for aperiodic CQI reports, LAA common information, notifications of MCCH change, UL power control commands for one cell and/or one RNTI, notification of a group of UEs 501 of a slot format, notification of a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE, TPC commands for PUCCH and PUSCH, and/or TPC commands for PUCCH and PUSCH. The DCI coding steps are discussed in 3GPP TS 38.212.

Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.

As alluded to previously, the PDCCH can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, wherein the DCI on PDCCH includes, inter alia, downlink assignments containing at least modulation and coding format, resource allocation, and HARQ information related to DL-SCH; and/or uplink scheduling grants containing at least modulation and coding format, resource allocation, and HARQ information related to UL-SCH. In addition to scheduling, the PDCCH can be used to for activation and deactivation of configured PUSCH transmission(s) with configured grant; activation and deactivation of PDSCH semi-persistent transmission; notifying one or more UEs 501 of a slot format; notifying one or more UEs 501 of the PRB(s) and OFDM symbol(s) where a UE 501 may assume no transmission is intended for the UE; transmission of TPC commands for PUCCH and PUSCH; transmission of one or more TPC commands for SRS transmissions by one or more UEs 501; switching an active BWP for a UE 501; and initiating a random access procedure.

In NR implementations, the UEs 501 monitor (or attempt to decode) respective sets of PDCCH candidates in one or more configured monitoring occasions in one or more configured CORESETs according to the corresponding search space configurations. A CORESET may include a set of PRBs with a time duration of 1 to 3 OFDM symbols. A CORESET may additionally or alternatively include N_(RB) ^(CORESET) RBs in the frequency domain and N_(symb) ^(CORESET) ϵ{1,2,3} symbols in the time domain. A CORESET includes six REGs numbered in increasing order in a time-first manner, wherein an REG equals one RB during one OFDM symbol. The UEs 501 can be configured with multiple CORESETS where each CORESET is associated with one CCE-to-REG mapping only. Interleaved and non-interleaved CCE-to-REG mapping are supported in a CORESET. Each REG carrying a PDCCH carries its own DMRS.

According to various embodiments, the UEs 501 and the RAN nodes 511 communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 501 and the RAN nodes 511 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs 501 and the RAN nodes 511 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs 501 RAN nodes 511, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 501, AP 506, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the BWs of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE 501 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The RAN nodes 511 may be configured to communicate with one another via interface 512. In embodiments where the system 500 is an LTE system (e.g., when CN 520 is an EPC), the interface 512 may be an X2 interface 512. The X2 interface may be defined between two or more RAN nodes 511 (e.g., two or more eNBs and the like) that connect to EPC 520, and/or between two eNBs connecting to EPC 520. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 501 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 501; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality. In embodiments where the system 100 is an MF system (e.g., when CN 520 is an NHCN 520), the interface 512 may be an X2 interface 512. The X2 interface may be defined between two or more RAN nodes 511 (e.g., two or more MF-APs and the like) that connect to NHCN 520, and/or between two MF-APs connecting to NHCN 520. In these embodiments, the X2 interface may operate in a same or similar manner as discussed previously.

In embodiments where the system 500 is a 5G or NR system (e.g., when CN 520 is an 5GC), the interface 512 may be an Xn interface 512. The Xn interface is defined between two or more RAN nodes 511 (e.g., two or more gNBs and the like) that connect to 5GC 520, between a RAN node 511 (e.g., a gNB) connecting to 5GC 520 and an eNB, and/or between two eNBs connecting to 5GC 520. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 501 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes 511. The mobility support may include context transfer from an old (source) serving RAN node 511 to new (target) serving RAN node 511; and control of user plane tunnels between old (source) serving RAN node 511 to new (target) serving RAN node 511. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN 510 is shown to be communicatively coupled to a core network—in this embodiment, CN 520. The CN 520 may comprise a plurality of network elements 522, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs 501) who are connected to the CN 520 via the RAN 510. The components of the CN 520 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 520 may be referred to as a network slice, and a logical instantiation of a portion of the CN 520 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 530 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 via the EPC 520.

In embodiments, the CN 520 may be a 5GC (referred to as “5GC 520” or the like), and the RAN 510 may be connected with the CN 520 via an NG interface 513. In embodiments, the NG interface 513 may be split into two parts, an NG user plane (NG-U) interface 514, which carries traffic data between the RAN nodes 511 and a UPF, and the Si control plane (NG-C) interface 515, which is a signaling interface between the RAN nodes 511 and AMFs.

In embodiments, the CN 520 may be a 5G CN (referred to as “5GC 520” or the like), while in other embodiments, the CN 520 may be an EPC). Where CN 520 is an EPC (referred to as “EPC 520” or the like), the RAN 510 may be connected with the CN 520 via an S1 interface 513. In embodiments, the S1 interface 513 may be split into two parts, an S1 user plane (S1-U) interface 514, which carries traffic data between the RAN nodes 511 and the S-GW, and the S1-MME interface 515, which is a signaling interface between the RAN nodes 511 and MMEs.

In embodiments where the CN 520 is an MF NHCN 520, the one or more network elements 522 may include or operate one or more NH-MMEs, local AAA proxies, NH-GWs, and/or other like MF NHCN elements. The NH-MME provides similar functionality as an MME in EPC 520. A local AAA proxy is an AAA proxy that is part of an NHN that provides AAA functionalities required for interworking with PSP AAA and 3GPP AAAs. A PSP AAA is an AAA server (or pool of servers) using non-USIM credentials that is associated with a PSP, and may be either internal or external to the NHN, and the 3GPP AAA is discussed in more detail in 3GPP TS 23.402. The NH-GW provides similar functionality as a combined S-GW/P-GW for non-EPC routed PDN connections. For EPC Routed PDN connections, the NHN-GW provides similar functionality as the S-GW discussed previously in interactions with the MF-APs over the S1 interface 513 and is similar to the TWAG in interactions with the PLMN PDN-GWs over the S2a interface. In some embodiments, the MF APs 511 may connect with the EPC 520 discussed previously. Additionally, the RAN 510 (referred to as an “MF RAN 510” or the like) may be connected with the NHCN 520 via an S1 interface 513. In these embodiments, the S1 interface 513 may be split into two parts, the S1-U interface 514 that carries traffic data between the RAN nodes 511 (e.g., the “MF-APs 511”) and the NH-GW, and the S1-MME-N interface 515, which is a signaling interface between the RAN nodes 511 and NH-MMEs. The S1-U interface 514 and the S1-MME-N interface 515 have the same or similar functionality as the S1-U interface 514 and the S1-MME interface 515 of the EPC 520 discussed herein.

FIG. 6 illustrates an example of infrastructure equipment 600 in accordance with various embodiments. The infrastructure equipment 600 (or “system 600”) may be implemented as a base station, radio head, RAN node such as the RAN nodes 511 and/or AP 506 shown and described previously, application server(s) 530, and/or any other element/device discussed herein. In other examples, the system 600 could be implemented in or by a UE.

The system 600 includes application circuitry 605, baseband circuitry 610, one or more radio front end modules (RFEMs) 615, memory circuitry 620, power management integrated circuitry (PMIC) 625, power tee circuitry 630, network controller circuitry 635, network interface connector 640, satellite positioning circuitry 645, and user interface 650. In some embodiments, the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.

Application circuitry 605 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor Interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors (or cores) of the application circuitry 605 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 600. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 605 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuitry 605 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein. As examples, the processor(s) of application circuitry 605 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior P-class processors; and/or the like. In some embodiments, the system 600 may not utilize application circuitry 605, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 605 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. As examples, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of application circuitry 605 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 605 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.

The baseband circuitry 610 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 610 are discussed infra with regard to FIG. 8.

User interface circuitry 650 may include one or more user interfaces designed to enable user interaction with the system 600 or peripheral component interfaces designed to enable peripheral component interaction with the system 600. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.

The radio front end modules (RFEMs) 615 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 811 of FIG. 8 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 615, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 620 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®. Memory circuitry 620 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.

The PMIC 625 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry 630 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 600 using a single cable.

The network controller circuitry 635 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment 600 via network interface connector 640 using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry 635 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 635 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry 645 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry 645 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 645 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 645 may also be part of, or interact with, the baseband circuitry 610 and/or RFEMs 615 to communicate with the nodes and components of the positioning network. The positioning circuitry 645 may also provide position data and/or time data to the application circuitry 605, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes 511, etc.), or the like.

The components shown by FIG. 6 may communicate with one another using interface circuitry, which may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus/IX may be a proprietary bus, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I²C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 7 illustrates an example of a platform 700 (or “device 700”) in accordance with various embodiments. In embodiments, the computer platform 700 may be suitable for use as UEs 501 a-b, application servers 530, and/or any other element/device discussed herein. The platform 700 may include any combinations of the components shown in the example. The components of platform 700 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 700, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 7 is intended to show a high level view of components of the computer platform 700. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

Application circuitry 705 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 705 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system 700. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 605 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry 605 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.

As examples, the processor(s) of application circuitry 705 may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, Calif. The processors of the application circuitry 705 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry 705 may be a part of a system on a chip (SoC) in which the application circuitry 705 and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

Additionally or alternatively, application circuitry 705 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 705 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 705 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.

The baseband circuitry 710 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry 710 are discussed infra with regard to FIG. 8.

The RFEMs 715 may comprise a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays (see e.g., antenna array 811 of FIG. 8 infra), and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical RFEM 715, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 720 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 720 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 720 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 720 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDlMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry 720 may be on-die memory or registers associated with the application circuitry 705. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 720 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform 700 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 723 may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform 700. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform 700 may also include interface circuitry (not shown) that is used to connect external devices with the platform 700. The external devices connected to the platform 700 via the interface circuitry include sensor circuitry 721 and electro-mechanical components (EMCs) 722, as well as removable memory devices coupled to removable memory circuitry 723.

The sensor circuitry 721 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs 722 include devices, modules, or subsystems whose purpose is to enable platform 700 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs 722 may be configured to generate and send messages/signalling to other components of the platform 700 to indicate a current state of the EMCs 722. Examples of the EMCs 722 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform 700 is configured to operate one or more EMCs 722 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform 700 with positioning circuitry 745. The positioning circuitry 745 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry 745 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 745 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 745 may also be part of, or interact with, the baseband circuitry 610 and/or RFEMs 715 to communicate with the nodes and components of the positioning network. The positioning circuitry 745 may also provide position data and/or time data to the application circuitry 705, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect the platform 700 with Near-Field Communication (NFC) circuitry 740. NFC circuitry 740 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 740 and NFC-enabled devices external to the platform 700 (e.g., an “NFC touchpoint”). NFC circuitry 740 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 740 by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 740, or initiate data transfer between the NFC circuitry 740 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 700.

The driver circuitry 746 may include software and hardware elements that operate to control particular devices that are embedded in the platform 700, attached to the platform 700, or otherwise communicatively coupled with the platform 700. The driver circuitry 746 may include individual drivers allowing other components of the platform 700 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 700. For example, driver circuitry 746 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 700, sensor drivers to obtain sensor readings of sensor circuitry 721 and control and allow access to sensor circuitry 721, EMC drivers to obtain actuator positions of the EMCs 722 and/or control and allow access to the EMCs 722, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 725 (also referred to as “power management circuitry 725”) may manage power provided to various components of the platform 700. In particular, with respect to the baseband circuitry 710, the PMIC 725 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 725 may often be included when the platform 700 is capable of being powered by a battery 730, for example, when the device is included in a UE 501 a-b.

In some embodiments, the PMIC 725 may control, or otherwise be part of, various power saving mechanisms of the platform 700. For example, if the platform 700 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 700 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 700 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform 700 may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery 730 may power the platform 700, although in some examples the platform 700 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 730 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 730 may be a typical lead-acid automotive battery.

In some implementations, the battery 730 may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 700 to track the state of charge (SoCh) of the battery 730. The BMS may be used to monitor other parameters of the battery 730 to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery 730. The BMS may communicate the information of the battery 730 to the application circuitry 705 or other components of the platform 700. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 705 to directly monitor the voltage of the battery 730 or the current flow from the battery 730. The battery parameters may be used to determine actions that the platform 700 may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 730. In some examples, the power block XS30 may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 700. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 730, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 750 includes various input/output (I/O) devices present within, or connected to, the platform 700, and includes one or more user interfaces designed to enable user interaction with the platform 700 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 700. The user interface circuitry 750 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 700. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry 721 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform 700 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG. 8 illustrates example components of baseband circuitry 810 and radio front end modules (RFEM) 815 in accordance with various embodiments. The baseband circuitry 810 corresponds to the baseband circuitry 610 and 710 of FIGS. 6 and 7, respectively. The RFEM 815 corresponds to the RFEM 615 and 715 of FIGS. 6 and 7, respectively. As shown, the RFEMs 815 may include Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, antenna array 811 coupled together at least as shown.

The baseband circuitry 810 includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry 806. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 810 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 810 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry 810 is configured to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. The baseband circuitry 810 is configured to interface with application circuitry 605/705 (see FIGS. 6 and 7) for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806. The baseband circuitry 810 may handle various radio control functions.

The aforementioned circuitry and/or control logic of the baseband circuitry 810 may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor 804A, a 4G/LTE baseband processor 804B, a 5G/NR baseband processor 804C, or some other baseband processor(s) 804D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors 804A-D may be included in modules stored in the memory 804G and executed via a Central Processing Unit (CPU) 804E. In other embodiments, some or all of the functionality of baseband processors 804A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory 804G may store program code of a real-time OS (RTOS), which when executed by the CPU 804E (or other baseband processor), is to cause the CPU 804E (or other baseband processor) to manage resources of the baseband circuitry 810, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry 810 includes one or more audio digital signal processor(s) (DSP) 804F. The audio DSP(s) 804F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

In some embodiments, each of the processors 804A-804E include respective memory interfaces to send/receive data to/from the memory 804G. The baseband circuitry 810 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry 810; an application circuitry interface to send/receive data to/from the application circuitry 605/705 of FIGS. 6-8); an RF circuitry interface to send/receive data to/from RF circuitry 806 of FIG. 8; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC 725.

In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry 810 comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry 810 may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules 815).

Although not shown by FIG. 8, in some embodiments, the baseband circuitry 810 includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry 810 and/or RF circuitry 806 are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry 810 and/or RF circuitry 806 are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 804G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry 810 may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry 810 discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuitry 810 may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry 810 and RF circuitry 806 may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry 810 may be implemented as a separate SoC that is communicatively coupled with and RF circuitry 806 (or multiple instances of RF circuitry 806). In yet another example, some or all of the constituent components of the baseband circuitry 810 and the application circuitry 605/705 may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry 810 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 810 may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodiments in which the baseband circuitry 810 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 806 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 806 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 806 may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 810. RF circuitry 806 may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry 810 and provide RF output signals to the FEM circuitry 808 for transmission.

In some embodiments, the receive signal path of the RF circuitry 806 may include mixer circuitry 806 a, amplifier circuitry 806 b and filter circuitry 806 c. In some embodiments, the transmit signal path of the RF circuitry 806 may include filter circuitry 806 c and mixer circuitry 806 a. RF circuitry 806 may also include synthesizer circuitry 806 d for synthesizing a frequency for use by the mixer circuitry 806 a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 806 a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806 d. The amplifier circuitry 806 b may be configured to amplify the down-converted signals and the filter circuitry 806 c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 810 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 806 a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 806 a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806 d to generate RF output signals for the FEM circuitry 808. The baseband signals may be provided by the baseband circuitry 810 and may be filtered by filter circuitry 806 c.

In some embodiments, the mixer circuitry 806 a of the receive signal path and the mixer circuitry 806 a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 806 a of the receive signal path and the mixer circuitry 806 a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 806 a of the receive signal path and the mixer circuitry 806 a of the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 806 a of the receive signal path and the mixer circuitry 806 a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 810 may include a digital baseband interface to communicate with the RF circuitry 806.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 806 d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 806 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 806 d may be configured to synthesize an output frequency for use by the mixer circuitry 806 a of the RF circuitry 806 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 806 d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 810 or the application circuitry 605/705 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 605/705.

Synthesizer circuitry 806 d of the RF circuitry 806 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 806 d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 806 may include an IQ/polar converter.

FEM circuitry 808 may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array 811, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing. FEM circuitry 808 may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of antenna elements of antenna array 811. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 806, solely in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.

In some embodiments, the FEM circuitry 808 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 808 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array 811.

The antenna array 811 comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry 810 is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array 811 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array 811 may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array 811 may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry 806 and/or FEM circuitry 808 using metal transmission lines or the like.

Processors of the application circuitry 605/705 and processors of the baseband circuitry 810 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 810, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 605/705 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.

FIG. 9 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 9 shows a diagrammatic representation of hardware resources 900 including one or more processors (or processor cores) 910, one or more memory/storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 902 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 900.

The processors 910 may include, for example, a processor 912 and a processor 914. The processor(s) 910 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 920 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 920 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 930 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 904 or one or more databases 906 via a network 908. For example, the communication resources 930 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 950 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 910 to perform any one or more of the methodologies discussed herein. The instructions 950 may reside, completely or partially, within at least one of the processors 910 (e.g., within the processor's cache memory), the memory/storage devices 920, or any suitable combination thereof. Furthermore, any portion of the instructions 950 may be transferred to the hardware resources 900 from any combination of the peripheral devices 904 or the databases 906. Accordingly, the memory of processors 910, the memory/storage devices 920, the peripheral devices 904, and the databases 906 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example 1 may include one or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE), cause the UE to: encode, for transmission to a gNB of a wireless cellular network on unlicensed spectrum, a physical random access channel (PRACH) preamble in a PRACH occasion; determine a random access response (RAR) window based on the PRACH occasion; receive a message in the RAR window, wherein the message includes a system frame number (SFN) indicator to indicate that the RAR message corresponds to the PRACH occasion; and process the RAR message based on the SFN indicator.

Example 2 may include the one or more NTCRM of Example 1 or some other example herein, wherein the message includes a downlink control information (DCI) scrambled with a random access radio network temporary identifier (RA-RNTI), and wherein the SFN indicator is included in the DCI.

Example 3 may include the one or more NTCRM of Example 2 or some other example herein, wherein the DCI has a DCI format 0_1.

Example 4 may include the one or more NTCRM of Example 2-3 or some other example herein, wherein the SFN indicator is included in an SFN field of the DCI.

Example 5 may include the one or more NTCRM of Example 1 or some other example herein, wherein the message includes a medium access control (MAC) RAR message, and wherein the SFN indicator is included in the MAC RAR message.

Example 6 may include the one or more NTCRM of Example 1-5 or some other example herein, wherein the SFN indicator is 2 bits and a length of the RAR window is 4 frames.

Example 7 may include the one or more NTCRM of Example 1-6 or some other example herein, wherein the message is a message 2 (Msg2) of a 4-step random access procedure, and wherein processing the Msg2 includes: determining that the Msg2 is for the UE based on the SFN indicator; and encoding a message 3 (Msg3) of the 4-step random access procedure based on the determination that the Msg 2 is for the UE.

Example 8 may include the one or more NTCRM of Example 1-6 or some other example herein, wherein the instructions, when executed, further cause the UE to encode a physical uplink shared channel (PUSCH) for transmission to the gNB with the PRACH preamble in a message A (MsgA) of a 2-step random access procedure; wherein the message is a message B (MsgB) of the 2-step random access procedure, wherein the MsgB includes a fallback random access response (fallbackRAR) or a success random access response (successRAR) wherein the SFN indicator is included in a downlink control information (DCI) or a medium access control (MAC) sub-protocol data unit (subPDU) of the MsgB.

Example 9 may include the one or more NTCRM of Example 8 or some other example herein, wherein the SFN indicator is included in the DCI of the MsgB.

Example 10 may include one or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB), cause the gNB to: receive, from a user equipment (UE) on unlicensed spectrum, a physical random access channel (PRACH) preamble in a PRACH occasion; determine a random access response (RAR) window based on the PRACH occasion; and encode a response message for transmission to the UE in the RAR window, wherein the response message includes a system frame number (SFN) indicator to indicate that the response message corresponds to the PRACH occasion.

Example 11 may include the one or more NTCRM of Example 10 or some other example herein, wherein the response message includes a downlink control information (DCI) scrambled with a random access radio network temporary identifier (RA-RNTI), and wherein the SFN indicator is included in the DCI.

Example 12 may include the one or more NTCRM of Example 11 or some other example herein, wherein the DCI has a DCI format 0_1.

Example 13 may include the one or more NTCRM of Example 11-12 or some other example herein, wherein the SFN indicator is included in a designated SFN field of the DCI.

Example 14 may include the one or more NTCRM of Example 10 or some other example herein, wherein the response message includes a medium access control (MAC) random access response (RAR) message.

Example 15 may include the one or more NTCRM of Example 10-14 or some other example herein, wherein the SFN indicator is 2 bits and a length of the RAR window is 4 frames.

Example 16 may include the one or more NTCRM of Example 10-15 or some other example herein, wherein the PRACH preamble is received in a message A (MsgB) of a 2-step random access procedure; wherein the response message is a message B (MsgB) that includes a fallback random access response (fallbackRAR) message or a success random access response (successRAR), wherein the SFN indicator is included in a downlink control information (DCI) or a medium access control (MAC) sub-protocol data unit (subPDU) of the MsgB.

Example 17 may include an apparatus to be implemented in a user equipment (UE), the apparatus comprising: a memory to store instructions for a random access procedure; and circuitry to execute the instructions to: encode, for transmission to a gNB of a wireless cellular network on unlicensed spectrum, a physical random access channel (PRACH) preamble; receive a downlink control information (DCI) in a random access response (RAR) window in response to the PRACH preamble, wherein the RAR window has a length of multiple frames, and wherein the DCI includes a system frame number (SFN) field to indicate an SFN associated with the DCI; and determine that the DCI is for the UE based on the SFN field.

Example 18 may include the apparatus of Example 17 or some other example herein, wherein the DCI is scrambled with a random access radio network temporary identifier (RA-RNTI) or MsgB radio network temporary identifier (MsgB-RNTI).

Example 19 may include the apparatus of Example 17-18 or some other example herein, wherein the DCI has a DCI format 0_1.

Example 20 may include the apparatus of Example 17-19 or some other example herein, wherein the SFN field is 2 bits and the length of the RAR window is 4 frames.

Example 21 may include the apparatus of Example 17-20 or some other example herein, wherein the random access procedure is a 4-step random access procedure.

Example 22 includes an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

Example 23 includes one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

Example 24 includes an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

Example 25 includes a method, technique, or process as described in or related to any of examples 1-21, or portions or parts thereof.

Example 26 includes an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.

Example 27 includes a signal as described in or related to any of examples 1-21, or portions or parts thereof.

Example 28 includes a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-21, or portions or parts thereof, or otherwise described in the present disclosure.

Example 29 includes a signal encoded with data as described in or related to any of examples 1-21, or portions or parts thereof, or otherwise described in the present disclosure.

Example 30 includes a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-21, or portions or parts thereof, or otherwise described in the present disclosure.

Example 31 includes an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.

Example 32 includes a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.

Example 33 includes a signal in a wireless network as shown and described herein.

Example 34 includes a method of communicating in a wireless network as shown and described herein.

Example 35 includes a system for providing wireless communication as shown and described herein.

Example 36 includes a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. 

1. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a user equipment (UE), cause the UE to: encode, for transmission to a gNB of a wireless cellular network on unlicensed spectrum, a physical random access channel (PRACH) preamble in a PRACH occasion; determine a random access response (RAR) window based on the PRACH occasion; receive a message in the RAR window, wherein the message includes a system frame number (SFN) indicator to indicate that the RAR message corresponds to the PRACH occasion; and process the RAR message based on the SFN indicator.
 2. The one or more NTCRM of claim 1, wherein the message includes a downlink control information (DCI) scrambled with a random access radio network temporary identifier (RA-RNTI), and wherein the SFN indicator is included in the DCI.
 3. The one or more NTCRM of claim 2, wherein the DCI has a DCI format 0_1.
 4. The one or more NTCRM of claim 2, wherein the SFN indicator is included in an SFN field of the DCI.
 5. The one or more NTCRM of claim 1, wherein the message includes a medium access control (MAC) RAR message, and wherein the SFN indicator is included in the MAC RAR message.
 6. The one or more NTCRM of claim 1, wherein the SFN indicator is 2 bits and a length of the RAR window is 4 frames.
 7. The one or more NTCRM of claim 1, wherein the message is a message 2 (Msg2) of a 4-step random access procedure, and wherein processing the Msg2 includes: determining that the Msg2 is for the UE based on the SFN indicator; and encoding a message 3 (Msg3) of the 4-step random access procedure based on the determination that the Msg 2 is for the UE.
 8. The one or more NTCRM of claim 1, wherein the instructions, when executed, further cause the UE to encode a physical uplink shared channel (PUSCH) for transmission to the gNB with the PRACH preamble in a message A (MsgA) of a 2-step random access procedure; wherein the message is a message B (MsgB) of the 2-step random access procedure, wherein the MsgB includes a fallback random access response (fallbackRAR) or a success random access response (successRAR) wherein the SFN indicator is included in a downlink control information (DCI) or a medium access control (MAC) sub-protocol data unit (subPDU) of the MsgB.
 9. The one or more NTCRM of claim 8, wherein the SFN indicator is included in the DCI of the MsgB.
 10. One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors of a next generation Node B (gNB), cause the gNB to: receive, from a user equipment (UE) on unlicensed spectrum, a physical random access channel (PRACH) preamble in a PRACH occasion; determine a random access response (RAR) window based on the PRACH occasion; and encode a response message for transmission to the UE in the RAR window, wherein the response message includes a system frame number (SFN) indicator to indicate that the response message corresponds to the PRACH occasion.
 11. The one or more NTCRM of claim 10, wherein the response message includes a downlink control information (DCI) scrambled with a random access radio network temporary identifier (RA-RNTI), and wherein the SFN indicator is included in the DCI.
 12. The one or more NTCRM of claim 11, wherein the DCI has a DCI format 0_1.
 13. The one or more NTCRM of claim 11, wherein the SFN indicator is included in a designated SFN field of the DCI.
 14. The one or more NTCRM of claim 10, wherein the response message includes a medium access control (MAC) random access response (RAR) message.
 15. The one or more NTCRM of claim 10, wherein the SFN indicator is 2 bits and a length of the RAR window is 4 frames.
 16. The one or more NTCRM of claim 10, wherein the PRACH preamble is received in a message A (MsgB) of a 2-step random access procedure; wherein the response message is a message B (MsgB) that includes a fallback random access response (fallbackRAR) message or a success random access response (successRAR), wherein the SFN indicator is included in a downlink control information (DCI) or a medium access control (MAC) sub-protocol data unit (subPDU) of the MsgB.
 17. An apparatus to be implemented in a user equipment (UE), the apparatus comprising: a memory to store instructions for a random access procedure; and circuitry to execute the instructions to: encode, for transmission to a gNB of a wireless cellular network on unlicensed spectrum, a physical random access channel (PRACH) preamble; receive a downlink control information (DCI) in a random access response (RAR) window in response to the PRACH preamble, wherein the RAR window has a length of multiple frames, and wherein the DCI includes a system frame number (SFN) field to indicate an SFN associated with the DCI; and determine that the DCI is for the UE based on the SFN field.
 18. The apparatus of claim 17, wherein the DCI is scrambled with a random access radio network temporary identifier (RA-RNTI) or MsgB radio network temporary identifier (MsgB-RNTI).
 19. The apparatus of claim 17, wherein the DCI has a DCI format 0_1.
 20. The apparatus of claim 17, wherein the SFN field is 2 bits and the length of the RAR window is 4 frames.
 21. The apparatus of claim 17, wherein the random access procedure is a 4-step random access procedure. 